Skip to content

bugfix: Normalize identifier usage for table names #4045

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

Mr-Destructive
Copy link
Contributor

Addressing issue #3936

  • Use identifier to get the table names consistent across all insert, update and other statements

Do you want to add tests for these? Thought would be a very specific test, so didn't add.
Let me know about the thoughts for this
Thanks

@dosubot dosubot bot added size:S This PR changes 10-29 lines, ignoring generated files. 🔧 golang labels Aug 7, 2025
@andrewmbenton
Copy link
Collaborator

Tests would be ideal. @kyleconroy may feel differently but I think because we already have an endtoend test for drop table statements it would be reasonable to just add a couple of statements to that test to cover this case.

As for the other failure cases, those are a bit more complicated and would require their own endtoend tests.

@dosubot dosubot bot added size:XL This PR changes 500-999 lines, ignoring generated files. and removed size:S This PR changes 10-29 lines, ignoring generated files. labels Aug 9, 2025
Copy link
Collaborator

@kyleconroy kyleconroy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding tests.

@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Aug 12, 2025
@kyleconroy kyleconroy merged commit fe96e12 into sqlc-dev:main Aug 12, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm This PR has been approved by a maintainer size:XL This PR changes 500-999 lines, ignoring generated files. 🔧 golang
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants